fix: prevent fragment FOUC by awaiting load before section reveal by shsteimer · Pull Request #77 · cloudadoption/diyfire

shsteimer · 2026-03-05T21:49:09Z

Summary

Move fragment loading from fire-and-forget in buildAutoBlocks to an awaitable loadFragments(section) callback passed to loadSection
Sections now wait for fragment content to load before becoming visible, preventing bare link flash
Restore sequential section loading (top-to-bottom) per boilerplate standard, replacing parallel Promise.all approach introduced in c455bed

Stacked on #76 — merge that first.

Test plan

Verify pages with auto-blocked fragments no longer flash bare links before content loads
Verify sections still reveal top-to-bottom sequentially
Verify #_dnb opt-out still works
Verify fragment block (non-auto-blocked) still works
Run PageSpeed on preview URL

Before/after: https://fix-fragment-fouc--diyfire--cloudadoption.aem.page

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com

Move fragment loading from fire-and-forget in buildAutoBlocks to an awaitable loadFragments(section) callback passed to loadSection. Sections now wait for fragment content before becoming visible. Also restores sequential section loading (top-to-bottom) per boilerplate standard, replacing the parallel Promise.all approach. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

aem-code-sync · 2026-03-05T21:49:13Z

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed.
In case there are problems, just click a checkbox below to rerun the respective action.